System and method for monitoring a battery status in a server in a data center

ABSTRACT

An information handling system includes a battery, a host processing complex, and a management system. The battery includes a battery power level gauge that determines a power level of the battery. The management system includes a wireless transceiver. When the host processing complex is unpowered, the management system is coupled to receive power from the battery and provides a first indication of the power level of the battery via the wireless transceiver.

FIELD OF THE DISCLOSURE

This disclosure generally relates to information handling systems, andmore particularly relates to a system and method for monitoring abattery status in a server in a data center.

BACKGROUND

As the value and use of information continues to increase, individualsand businesses seek additional ways to process and store information.One option is an information handling system. An information handlingsystem generally processes, compiles, stores, and/or communicatesinformation or data for business, personal, or other purposes. Becausetechnology and information handling needs and requirements may varybetween different applications, information handling systems may alsovary regarding what information is handled, how the information ishandled, how much information is processed, stored, or communicated, andhow quickly and efficiently the information may be processed, stored, orcommunicated. The variations in information handling systems allow forinformation handling systems to be general or configured for a specificuser or specific use such as financial transaction processing,reservations, enterprise data storage, or global communications. Inaddition, information handling systems may include a variety of hardwareand software resources that may be configured to process, store, andcommunicate information and may include one or more computer systems,data storage systems, and networking systems.

BRIEF DESCRIPTION OF THE DRAWINGS

It will be appreciated that for simplicity and clarity of illustration,elements illustrated in the Figures have not necessarily been drawn toscale. For example, the dimensions of some of the elements areexaggerated relative to other elements. Embodiments incorporatingteachings of the present disclosure are shown and described with respectto the drawings presented herein, in which:

FIG. 1 is a view of a server rack according to an embodiment of thepresent disclosure;

FIG. 2 is a block diagram illustrating a management system of the serverrack of FIG. 1;

FIG. 3 is an illustration of an OSI layer arrangement of the managementsystem of FIG. 2;

FIGS. 4 and 5 are block diagrams of various embodiments of wirelessWiFi-based management networks on the management system of FIG. 2;

FIG. 6 is an illustration of a Bluetooth® stack arrangement of themanagement system of FIG. 2;

FIG. 7 is a block diagram of a Bluetooth®-based management network onthe management system of FIG. 2;

FIG. 8 is a block diagram illustrating a generalized informationhandling system according to an embodiment of the present disclosure;

FIG. 9 is a block diagram illustrating an embodiment of a managementsystem of the information handling system of FIG. 8;

FIG. 10 is a block diagram illustrating the management system of FIG. 2,and a method for provisioning and inventorying a powered off server in adata center; and

FIG. 11 is a flowchart illustrating a method for monitoring a batterystatus in a server in a data center according to an embodiment of thepresent disclosure.

The use of the same reference symbols in different drawings indicatessimilar or identical items.

DETAILED DESCRIPTION OF DRAWINGS

FIG. 1 illustrates an embodiment of a server rack 100 including a bladechassis 110, a server 130, and storage 140 situated in a rack space ofthe server rack, and a top-of-rack (ToR) switch 150 at the top of theserver rack. The rack space represents a standard server rack, such as a19-inch rack equipment mounting frame or a 23-inch rack equipmentmounting frame, and includes rack units, or divisions of the rack spacethat are a standardized unit of 1.75 inches high. For example, a pieceof equipment that will fit an one of the rack units is referred to as a1-U piece of equipment, another piece of equipment that takes up two ofthe rack units is referred to as a 2-U piece of equipment, and so forth.As such, the rack units are numbered sequentially from the bottom to thetop as 1U, 2U, 3U, 4U, 5U, and 6U. The skilled artisan will recognizethat other configurations for the rack units can be utilized as neededor desired. For example, a rack unit can be defined by the ElectronicComponents Industry Association standards council.

Blade chassis 110 represents a processing system of server rack 100 thatis configured as a number of modular processing resources, or blades,that are provided in a common frame (i.e., the chassis). As such, bladechassis 110 includes server blades 120, 122, 124, and 126. Server 130represents another processing system of server rack 100 that isconfigured as an individual processing resource. Storage 140 representsa data storage capacity of server rack 100 that provides a number ofdisk drives that are configured to the use of blade chassis 110 and ofserver 130, and can include other type of storage resource for serverrack 100.

ToR switch 110 represents a network system of server rack 100, providingfor high speed communications between blade chassis 110, server 130,storage 140, and a network (not illustrated). In particular, ToR switch150 is connected to blade chassis 110, server 130, and storage 140 via anetwork fabric (not illustrated), to provide data routing between theelements.

Each element of server rack 100 includes a management system having amanagement controller and a wireless management module. As such, bladechassis 110 includes a chassis management system 111 with a chassismanagement controller 112 and a wireless management module 114, server130 includes a server management system 131 with a server managementcontroller 132 and a wireless management module 134, storage 140includes a storage management system 111 with a storage managementcontroller 142 and a wireless management module 144, and ToR switch 150includes a ToR management system 151 that includes a ToR managementcontroller 152 and a wireless management module 154. Each of wirelessmanagement modules 114, 134, 144, and 154 include a respectiveactivation switch 116, 136, 146, and 156, and respective indicators 118,138, 148, and 158, described further, below.

Management systems 111, 131, 141, and 151 are connected together via amanagement network 160 to provide for out-of-band monitoring,management, and control of the respective elements of server rack 100.For example, management systems 111, 131, 141, and 151 can providesystem monitoring functions, such as temperature monitoring, powersupply monitoring, physical intrusion monitoring, hot-swap and hot-plugmonitoring, other monitoring functions that can be performed outside ofa hosted environment of the respective elements of server rack 100, orother system monitoring functions as needed or desired. Managementsystems 111, 131, 141, and 151 can also provide system management andcontrol functions for the respective elements of server rack 100, suchas cooling fan speed control, power supply management, hot-swap andhot-plug management, firmware management and update management forsystem BIOS or UEFI, Option ROM, device firmware, and the like, or othersystem management and control functions as needed or desired. As such,management controllers 112, 132, 142, and 152 represent embeddedcontrollers associated with the respective elements of server rack 100that operate separately from a hosted processing environment of therespective elements. For example, management controllers 112, 132, 142,and 152 can include a baseboard management controller (BMC), anIntegrated Dell Remote Access Controller (IDRAC), or another type ofmanagement controller as needed or desired. Further, managementcontrollers 112, 132, 142, and 152 can operate in accordance with anIntelligent Platform Management Interface (IPMI) specification, a WebServices Management (WSMAN) standard, or another interface standard forembedded management systems, as needed or desired. The skilled artisanwill recognize that management controllers 112, 132, 142, and 152 caninclude other circuit elements, devices, or sub-systems, such as anembedded controller, a logic device such as a Programmable Array Logic(PAL) device, a Complex Programmable Logic Device (CPLD), aField-Programmable Gate Array (FPGA) device, or the like, multiplexors,and other devices as needed or desired to provide the functions andfeatures as described herein.

Wireless management modules 114, 134, 144, and 154 operate to providewireless connectivity between a user with a wireless enabled mobiledevice 170 and management network 160 through the respective managementcontrollers 112, 132, 142, and 152. For example, wireless managementmodules 114, 134, 144, and 154 can include WiFi wireless interfaces inaccordance with one or more IEEE 802.11 specifications for high-speeddata communication between mobile device 170 and the wireless managementmodules, at speeds of up to 30 mega-bits per second (MBPS) or more.Wireless management modules 114, 134, 144, and 154 can also includeBluetooth® wireless interfaces in accordance with one or more Bluetooth®specifications, including Bluetooth® Low Energy (BLE), also known asBluetooth® Smart (BTS), for lower-speed communications at speeds of upto 150 kilo-bits per second (Kbps) or more.

Wireless management modules 114, 134, 144, and 154 include varioussecurity features to ensure that the connection between mobile device170 and management network 160 is secure and that the user of the mobiledevice is authorized to access the resources of the management network.In particular, wireless management modules 114, 134, 144, and 154operate to provide various WiFi user and device authentication schemes,such as schemes that are in accordance with one or more IEEE 802.11specifications, Service Set Identification (SSID) hiding, Media AccessControl Identification (MAC ID) filtering to allow only pre-approveddevices or to disallow predetermined blacklisted devices, StaticInternet Protocol (IP) addressing, Wired Equivalent Privacy (WEP)encryption, WiFi Protected Access (WPA) or WPA2 encryption, TemporaryKey Integrity Protocol (TKIP) key mixing, Extensible AuthenticationProtocol (EAP) authentication services, EAP variants such asLightweight-EAP (LEAP), Protected-EAP (PEAP), and other standard orvendor specific user and device authentication schemes, as needed ordesired. Further, wireless management modules 114, 134, 144, and 154operate to provide various Bluetooth® device and service authenticationschemes, such as a Security Mode 2 service level-enforced security modethat may be initiated after link establishment but before logicalchannel establishment, a Security Mode 3 link level-enforced securitymode that may be initiated before a physical link is fully established,a Security Mode 4 service level-enforced security mode that may beinitiated after link establishment but before logical channelestablishment and that uses a Secure Simple Pairing (SSP) protocol, orother device or service authentication schemes, as needed or desired.

In a particular embodiment, wireless management modules 114, 134, 144,and 154 also provide additional security features that further assurethe user, device, and service security of the connection between mobiledevice 170 and management network 160. In particular, wirelessmanagement modules 114, 134, 144, and 154 each include an activationswitch 116, 136, 146, and 156, respectively, that operate to enable theestablishment of the connection between the mobile device and thewireless management modules. In this way, the establishment of theconnection between mobile device 170 and wireless management modules114, 134, 144, and 154 is predicated on the physical proximity of a userand of the user's mobile device to server rack 100, and also upon anaction indicating a request to establish the connection. Here, a remotedevice and user would not be able to initiate an attack on managementnetwork 160 because of the lack of physical proximity to server rack 100to activate activation switches 116, 136, 146, or 156, and so anyattempt to attack management network would have to wait at least until aservice technician activated one of the activation switches. In anotherembodiment, one or more of wireless management modules 114, 134, 144,and 154 and mobile device 170 operate to detect a Received SignalStrength Indication (RSSI) or a Received Channel Power Indication (RCPI)to permit the determination of the proximity between the mobile deviceand the wireless management modules, as described further, below. In aparticular embodiment, one or more of wireless management modules 114,134, 144, and 154 does not include an activation switch, and theparticular wireless management modules provide for the establishment ofthe connection between the mobile device the wireless management modulesin response to another activation request from the mobile device.

The elements of server rack 100, blade chassis 110, server 130, storage140, and ToR switch 150 are exemplary, and more or fewer elements can beconsidered to be included in the server rack as needed or desired, andthat other types of elements can be included in the server rack asneeded or desired. Further, the management network of server rack 100can include management controllers associated with more or fewerelements or different types of elements, and needed or desired.

FIG. 2 illustrates a management system 200 similar to management systems111, 131, 141, and 151, and includes a management controller 210 that issimilar to management controllers 112, 132, 142, and 152, a wirelessmanagement module 240 similar to wireless management modules 114, 134,144, and 154, a USB connector 202, a wireless device antenna 204, and aconnection to a management network 206. Management controller 210includes a USB multiplexor 212, a CPLD 214, and an embedded controller220. Embedded controller 220 includes a USB interface 222, a resetfunction output 224, an interrupt request input 226, a managementnetwork interface device (NIC) 228, an Inter-Integrated Circuit (I2C)interface 230, and a General Purpose I/O (GPIO) 232.

Wireless management module 240 includes a 20 megahertz (MHz) crystal242, a system ID module 244, indicators 246, an activation switch 248, amicro-controller 250, and a wireless transceiver module 270.Micro-controller 250 includes a USB interface 252, a reset functioninput 254, GPIOs 256 and 266, an I2C interface 258, a Secure Digital I/O(SDIO) interface 260, a Universal Asynchronous Receiver/Transmitter(UART) 262, and a crystal input 264. Wireless transceiver module 270includes and SDIO interface 72, a UART 274, a WiFi transceiver 276, aBluetooth® transceiver 278, and a Radio Frequency (RF) switch 280.Management controller 210 and wireless management module 240 will beunderstood to include other elements, such as memory devices, powersystems, and other elements as needed or desired to perform theoperations as described herein. In a particular embodiment, wirelessmanagement module 240 is configured as a pluggable module that can beinstalled into management system 200, or not, as needed or desired bythe user of a rack system that includes the management system. Theskilled artisan will recognize that other configurations can beprovided, including providing one or more element of managementcontroller 210 or wireless management module 240 as a pluggable module,as elements on a main board of management system 200, or as integrateddevices of the management system.

USB multiplexor 212 is connected to USB connector 202, and USBinterfaces 222 and 252 to make a selected point-to-point USB connection.For example, a connection can be made between a USB device plugged in toUSB connector 202 and embedded controller 220 by connecting the USBconnector to USB interface 222. In this way, a device plugged in to USBconnector 202 can access the management functions and features of theinformation handling system that is managed by management controller210, and can access management network 206. Alternatively, a connectioncan be made between a USB device plugged in to USB connector 202 andmicro-controller 250 by connecting the USB connector to USB interface252. In this way, a device plugged in to USB connector 202 can accessthe management functions and features of wireless management module 240.For example, a technician in a data center can connect a laptop deviceto USB connector 202, configure USB multiplexor 212 to make apoint-to-point connection to USB interface 252, and provide a firmwareupdate for wireless management module 240. Finally, a connection can bemade between embedded controller 220 and micro-controller 250 byconnecting USB interface 222 to USB interface 222. In this way, a mobiledevice 290 that has established a wireless connection to wirelessmanagement module 240 can access the management functions and featuresof the information handling system that is managed by management system200, the mobile device can access management network 206, and themanagement network can be used to access the management functions andfeatures of the wireless management module or to provide a firmwareupdate for the wireless management module. USB connector 202, USBmultiplexor 212, and USB interfaces 222 and 252 can be configured inaccordance with the USB Standard Revision 3.1, or with another USBStandard Revision, as needed or desired. In updating the firmware ofwireless management module 240, micro-controller 250 operates to provideversion retrieval, fail-safe updating, signature validation, and otheroperations needed or desired to perform the firmware update of thewireless management module. In a particular embodiment, managementcontroller 210 does not include USB multiplexor 212, and USB interfaces222 and 252 are directly connected together.

CPLD 214 represents a logic device for implementing custom logiccircuitry to interface between various off-the-shelf integratedcircuits, and particularly between embedded controller 220 andmicro-controller 250. In particular, CPLD 214 operates to receive asystem identification input (SYS_ID) from wireless management module240, to receive the reset signal from reset function output 224, toforward the reset signal to reset function input 254, to receive amodule present (PRESENT) signal from the wireless management module, andto receive an interrupt (INT) signal from GPIO 256. The SYS_ID can beprovided based upon one or more settings, such as jumper settings,fusible links, register settings, or other settings, as needed ordesired. In another embodiment, one or more functions of CPLD 214 isprovided by embedded controller 220, or by micro-controller 250, asneeded or desired.

Embedded controller 220 represents an integrated device or devices thatis utilized to provide out-of-band management functions to theinformation handling system that includes management system 200, and caninclude a BMC, an IDRAC, or another device that operates according tothe IPMI specification. In particular, embedded controller 220 operatesto receive an interrupt alert (ALERT) signal from GPIO 258 on interruptrequest input 230, to send and receive information between I2C 230 andI2C 258, and to receive system status information and systemidentification information (SYS_STATUS/SYS_ID) from system ID module244.

Micro-controller 250 represents an embedded controller that operates tocontrol the functions and features of wireless module 240, as describedfurther, below. Micro-controller 250 operates to send and receiveinformation between SDIO interface 260 and SDIO interface 272, to sendand receive information between UART 262 and UART 274, to receive acrystal clock signal input from crystal 242, to provide control outputsfrom GPIO 266 to indicators 246, and to receive an activation input fromactivation switch 248 at GPIO 266. Indicators 246 provide visualindications of various statuses for wireless management module 240,including a health indication, a electrical/power indication, atemperature indication, a memory status indication, and a radio statusindication that identifies the type of a mobile device that is connectedto wireless management module, such as a WiFi device, a Bluetooth®device, or a Near Field Communication (NFC) device. In a particularembodiment, micro-controller 250 provides other modes of communicationbetween management controller 210 and wireless transceiver module 270,as needed or desired.

Wireless transceiver module 270 represents a mixed-signal integratedcircuit device that operates to provide the radio signal interface to amobile device 290 and to provide data interfaces to micro-controller250. As such, wireless transceiver module 270 includes a WiFi channelthat includes SDIO interface 272 and WiFi transceiver 276, and aBluetooth® channel that includes UART 274 and Bluetooth® transceiver 278that each are connected to RF switch 280. RF switch 280 switches antenna204 to selectively provide WiFi communications or Bluetooth®communications to mobile device 290. In a particular embodiment,wireless transceiver module 270 represents an off-the-shelf device toprovide WiFi and Bluetooth® wireless communications with mobile device290.

Management controller 210 operates to provide management andconfiguration of wireless management module 240, such as by providingfirmware updates, SSID configuration, WEP or WPA2 passwords, and thelike. In interfacing with management controller 210, wireless managementmodule 240 is represented as a composite USB device, and is connected astwo different devices to the management controller. In operating with aWiFi connected mobile device, such as mobile device 290, managementcontroller 210 instantiates a USB class NIC device driver, and themanagement controller treats the wireless management module inaccordance with an Ethernet Remote Network Driver InterfaceSpecification (RNDIS), a USB Communication Device Class (CDC) device, aUSB NIC, or another USB network class device. Thus, as viewed frommanagement controller 210, wireless management module 240 operate as aUSB NIC, and as viewed from mobile device 290 the wireless managementmodule operates as a WiFi class device, as described further below.

In operating with a Bluetooth® connected mobile device, such as mobiledevice 290, management controller 210 acts as Bluetooth® HostController, using a Host Controller Interface (HCI) protocol tocommunicate with wireless management module 240 via a serial port(UART). In another embodiment, wireless management module 240 is viewedby management controller 210 as a Bluetooth® dongle. Thus, as viewedfrom management controller 210, wireless management module 240 operateas a USB CDC, and as viewed from mobile device 290 the wirelessmanagement module operates as a Bluetooth® device, as described furtherbelow.

Wireless management module 240 operates to deactivate one or more of theWiFi stack and the Bluetooth® stack in response to a timeout event. Assuch, micro-controller 250 can include a timer that determines if aconnected device has gone dormant or otherwise ceased to interact withmanagement system 200, such as when mobile device 290 has moved out ofrange of wireless management module 240. Here, wireless managementmodule 240 can suspend the connected session with the mobile device, andno new session will be initiated until activation switch 248 isactivated to indicate that a new session is requested. For example, whena user who is connected using mobile device 290 with management system200, but subsequently walks away from a server rack that includes themanagement system, wireless management module 240 can automaticallydetect the time that the connection is idle, and, after a predeterminedduration, can shut down the connection and suspend all wireless activityuntil a new session is requested. Further, wireless management module240 operates such that a selected one or both of the WiFi stack and theBluetooth® stack can be disabled. In a particular embodiment, wirelessmanagement module 240 operates to configure the transmission power levelof the WiFi channel and of the Bluetooth® channel.

Mobile device 290 represents a wireless communication enabled device,such as a tablet device, a laptop computer, a smart phone, and the like,that is configured to interact with management system 200 via a wirelessconnection to wireless management module 240. In particular, mobiledevice 290 can include a mobile operating system (OS), such as anAndroid OS, an iOS, a Windows mobile OS, or another mobile OS that isconfigured to operate with the hardware of the mobile device. As such,the hardware of mobile device 290 can include Android-enabled hardware,iOS-enabled hardware, Windows-enabled hardware, or other hardware, asneeded or desired.

FIG. 3 illustrates management system 200, including the stack up of anOpen Systems Interconnection (OSI) communication model layer arrangementfor the management system. Here, the physical layer (L1) 310 and thelink layer (L2) 320 are included in the functionality of wirelessmanagement module 240, and the network layer (L3) 330, the transportlayer (L4) 340, the session layer (L5) 350, the presentation layer (L6)360, and the application layer (L7) 370 are included in managementcontroller 210.

FIG. 4 illustrates an embodiment of a wireless WiFi-based managementnetwork 400 on management system 200. Here, wireless management module240 presents itself to management controller 210 as a USB NICfunctionality, and the management controller is illustrated as providinga USB NIC functionality by including a USB CDC/RNDIS Ethernet driver420, a MAC address 422, an IP address 424 (192.168.2.2), a TransmissionControl Protocol (TCP) and User Datagram Protocol (UDP) layer 426, andan application layer 428. Management controller 210 is also illustratedas providing an I2C interface including an I2C driver 430 and a wirelessprovisioner 432. Note that the IP address can be an IP version 4 (IP4)address, as illustrated, or an IP version 6 (IPV6) address, as needed ordesired. Wireless management module 240 operates independently frommanagement controller 210 in establishing and maintaining WiFi-basedmanagement network 400.

In establishing WiFi-based management network 400, wireless managementmodule 240 is configured as a wireless access point that allows multiplemobile devices to be connected to management system 200. As such,management system 200 is illustrated as being connected with mobiledevices 410, 412, and 414. Wireless management module 240 provides WiFisecurity functionality to mobile devices 410, 412, and 414, such as byscreening the WIFI SSID so that only mobile devices that are aware ofthe existence of the wireless management module can be provide a requestto be connected, by providing a key secured establishment of theconnection, by encrypting communications between the mobile devices andthe wireless management module using WEP, WPA, WPA2, or anotherencryption protocol, by providing other security assurance functions andfeatures, or a combination thereof.

In addition, wireless management module 240 operates as a Dynamic HostConfiguration Protocol (DHCP) host that provides a unique IP address toconnected mobile devices 410, 412, and 414, the wireless managementmodule can establish the connections with the mobile devices based uponstatic IP addresses of the mobile devices, or the wireless managementmodule can provide a sub-network using a combination of DHCP-provided IPaddresses and static IP addresses, as needed or desired. Further,wireless management module 240 views management controller 210 as aseparate IP endpoint and can provide the management controller with aDHCP-provided IP address or the management controller can include astatic IP address as needed or desired. In another embodiment,management controller 210 operates as a DHCP host that provides IPaddresses to connected mobile devices 410, 412, and 414. In a particularembodiment, the DHCP host operates in accordance with the DHCPv6specification, in a stateless auto-configuration mode, or another IPprotocol.

Further, wireless management module 240 operates as a Layer-2 switchthat redirects packets on the sub-network to the targeted endpoints. Assuch, mobile devices 410, 412, and 414, wireless management module 240,and management controller 210 can communicate with each other on thesub-network provided by the wireless management module. Also, wirelessmanagement module 240 operates to distribute gateway information tomobile devices 410, 412, and 414, and to management controller 210.Further, wireless management module 240 supports blacklisting andwhitelisting of specific IP addresses that request access to managementsystem 200.

In a particular embodiment, management controller 210 operates toprovide various configuration information to wireless management module240 via wireless provisioner 432, which tunes and controls the behaviorof the wireless management module over the I2C bus. As such, managementcontroller 210 can provide SSIDs, security keys, gateway addresses, andother configuration information, to wireless management module 240 viaone of USB interfaces 212 and 252, and I2C interfaces 230 and 258. Here,because USB interfaces 212 and 252 and I2C interfaces 230 and 258 arewithin a server rack, and thus are deemed to be secure, wirelessmanagement module 240 does not need to employ additional securitymeasures in accepting such configuration information from managementcontroller 210. In another embodiment, wireless management module 240receives the various configuration information from one or more ofmobile devices 410, 412, and 414. Here, because a connection betweenwireless management module 240 and mobile devices 410, 412, and 414 isless secure than the connection to management controller 210, thewireless management module includes a management mode that is accessedvia additional security and authentication functions and features inorder to ensure that the users of the mobile devices are authorized tomake such configuration modifications. For example, the management modecan be accessed via an additional username and password verification,via a hardware device authentication, or another mechanism for providingsecurity and authentication, as needed or desired. In anotherembodiment, communications between management controller 210 andwireless management module 250 is conducted by other communicationinterfaces than USB interfaces 212 and 252, and I2C interfaces 230 and258, as needed or desired.

A method of providing WiFi-based management network 400 on managementsystem 200 includes powering on the management system, and determiningthat wireless management module 240 is installed into the managementsystem. If wireless management system 240 is installed, then managementcontroller 210 issues a DHCP request to connect to the access point thatis established on the wireless management module. Wireless managementmodule 240 assigns an IP address (192.168.2.2) to management controller210 that is in the same sub-network as the access point (192.168.2.1).Next, mobile device 410 issues a DHCP request to connect to the accesspoint and wireless management module 240 assigns an IP address(192.168.2.3) to the mobile device. Similarly, mobile devices 412 and414 issue DHCP requests to connect to the access point and wirelessmanagement module 240 assigns IP addresses (192.168.2.4 and 192.168.2.5)to the mobile devices. In this way, management controller 210, wirelessmanagement module 240, and mobile devices 410, 412, and 414 cancommunicate over the sub-network with each other.

FIG. 5 illustrates another embodiment of a wireless-based managementnetwork 500 on management system 200. WiFi based management network 500includes the functions and features of WiFi based management network400, where wireless management module 240 operates in an access pointmode to form a sub-network with mobile devices 410, 412, and 414. Inaddition to establishing WiFi-based management network 400, wirelessmanagement module 240 is configured as a wireless base station thatpermits the wireless management module to connect to a wirelessmanagement network 520 on a different sub-network. In the wireless basestation mode, wireless management module 240 operates as a wirelessclient to wireless management network 520, such that the wirelessmanagement module operates to provide a DHCP request and authenticationcredentials to the wireless management network, and is authenticated bythe wireless management network. Here, wireless management module 240operates as a router that permits mobile devices 410, 412, and 414, andmanagement controller 210 to communicate with wireless managementnetwork 520. In another embodiment, management controller 210 operatesas the router, as needed or desired.

In a particular embodiment, management controller 210 is established asa node on wireless management network 520. Here, in one case, managementcontroller 210 can be initially connected to, and established as a nodeon management network 520 through wireless management module 240, andthen the wireless management module can establish the access pointsub-network with mobile devices 410, 412, and 414. In another case,wireless management module 240 can establish the access pointsub-network with mobile devices 410, 412, and 414, and managementcontroller 210, as described above. Then, management controller 210 canperform a USB disconnect and a USB reconnect to wireless managementmodule 240, and can send a DHCP request and authentication credentialsto wireless management network 520 to obtain an IP address that is onthe sub-network of the wireless management network.

A method of providing WiFi-based management network 500 on managementsystem 200 includes the method for providing WiFi-based managementnetwork 400, as described above. After management controller 210,wireless management module 240, and mobile devices 410, 412, and 414 areestablished on the first sub-network, the management controller directsthe wireless management module 240 to operate in a concurrent accesspoint and base station mode. Wireless management module 240 thendisconnects from the USB interface and reconnects to the USB interfacewith management module 210, and the management module sends SSID andauthentication information to the wireless management module. Wirelessmanagement module 240 then sends a DHCP request and the authenticationinformation to wireless management network 520. Wireless managementnetwork 520 sends an IP address (10.35. 17.X) to management controller210 and authenticates the management controller onto the newsub-network. Here, because wireless management module 240 operates as arouter, mobile devices 410, 412, and 414 can also communicate withwireless management network 520.

FIG. 6 illustrates management system 200, including the stack up of aBluetooth® communication arrangement for the management system. Here,the application 610 and the host 620 are included in the functionalityof management controller 210, and the controller 630 is included in thefunctionality of wireless management module 240.

FIG. 7 illustrates an embodiment of a wireless Bluetooth® basedmanagement network 700 on management system 200. Here, wirelessmanagement module 240 presents itself to management controller 210 as aUSB COM port functionality, and the management controller is illustratedas including a Bluetooth® USB HCI layer 720, Bluetooth® Low Energy (BLE)host OSI layers 722, and Bluetooth® Generic Attribute Profiles (GATT)724. Management controller 210 is also illustrated as providing I2Cdriver 430 and wireless provisioner 432, which tunes and controls thebehavior of the wireless management module over the I2C bus. Wirelessmanagement module 240 operates independently from management controller210 in establishing and maintaining Bluetooth®-based management network700.

In establishing Bluetooth®-based management network 700, wirelessmanagement module 240 is configured as a Bluetooth® controller inaccordance with a Bluetooth® Core Specification, and can connect asingle mobile device 710 to management system 200. Management controller210 operates to provide and maintain the BLE beacon data, content, andpass keys in wireless management module 240, and directs the wirelessmanagement module to change between operating modes, such as anadvertising mode, a scanning mode, a master mode, a slave mode, oranother operating mode, as needed or desired. In a particularembodiment, wireless management module 240 operates to configure thetransmission power level of the Bluetooth® channel, and supports RSSIand RCPI reporting on the incoming signal from mobile device 710.Further, wireless management module 240 supports blacklisting andwhitelisting of specific mobile devices that request access tomanagement system 200, such as by identifying a particular MAC address,IP address, International Mobile-station Equipment Identity (IMEI),Mobile Equipment Identifier (MEID), or other unique identifier for amobile device.

FIG. 10 illustrates a management system 1000 similar to managementsystem 200, and that includes a management controller 1010 similar tomanagement controller 210, a wireless management module 1040 similar towireless management module 240, a memory device 1070, a battery 1080, abattery and power manager and timer module 1085, a USB connector 1002, awireless device antenna 1004, and a managed device 1006 of theinformation handling system that includes the management system.Management controller 1010 is similar to management controller 210, andincludes a USB multiplexor 1012, and an embedded controller 1020.Embedded controller 1020 includes a USB interface 1022, an I2C interface1024, and a device I/O interface 1026. USB multiplexor 1012 is connectedto USB connector 1002, and to USB interfaces 1022 and 1052 to make aselected point-to-point USB connection. Here, USB multiplexor 1012 isillustrated as including a provision mode input 1014 that connects USBconnector 1002 directly to USB interface 1052 when management controller1010 is in a powered-off provisioning mode.

Wireless management module 1040 is similar to wireless management module240, and includes a micro-controller 1050, and a wireless transceivermodule 1070. Micro-controller 1050 includes a USB interface 1052, and anI2C interface 1054. Management controller 1010 and wireless managementmodule 1040 will be understood to include other elements, such as memorydevices, power systems, and other elements as needed or desired toperform the operations as described herein. Wireless transceiver module1070 represents a mixed-signal integrated circuit device that operatesto provide the radio signal interface to a mobile device 1090 and toprovide data interfaces to micro-controller 1050.

Memory device 1070 can include a non-volatile memory device, such as anNVRAM device, a Flash device, or another non-volatile memory device thatretains data stored therein when the power to wireless management system1000 is powered off. Memory device 1070 can also include a volatilememory device that retains data stored therein when the power towireless management system 1000 is powered off by receiving a dataretention power level from battery 1080. Battery 1080 is also connectedto selectively provide power to management controller 1010, to wirelessmodule 1040, and to managed device 1006, as needed or desired. Batteryand power manager and timer 1085 operates to manage the charge anddischarge operations of battery 1080. In managing the charge anddischarge operations of battery 1080, battery and power manager andtimer 1085 operates in accordance with various battery managementtechniques and procedures as are known to the skilled artisan, and asdictated by the type of battery 1080.

Battery and power manager and timer 1085 also operates to determine whenand how to selectively connect battery 1080 to management controller1010, to wireless management module 1040, and to managed device 1006. Inparticular, battery and power manager and timer 1085 provides a wirelesscommunication mode wherein battery 1080 is connected to wirelessmanagement module 1040, such that the wireless management module isprovided with sufficient power to operate wireless transceiver module1070 to establish and maintain a wireless connection with mobile device1090, to operate micro-controller 1050 to receive information from themobile device and to store the received information in memory device1070, and to the operate micro-controller to retrieve information fromthe memory device and to transmit the retrieved information to themobile device. In a particular embodiment, in the wireless communicationmode, battery 1080 is also connected to management controller 1010 andto managed device 1006, such the management controller is provided withsufficient power to operate embedded controller 1020 to retrieveinformation from memory device 1070 and to store the retrievedinformation to the managed device, and to operate the embeddedcontroller to load information from the managed device and to store theloaded information to the memory device. In another embodiment, in thewireless communication mode, battery and battery 1080 is also connectedto management controller 1010 and to managed device 1006, such themanagement controller is provided with sufficient power to operateembedded controller 1020 to receive information from mobile device 1090via micro-controller 1050 and to store the received information in themanaged device, and to operate the embedded controller to loadinformation from the managed device and to transmit the loadedinformation to the mobile device via the micro-controller. Note that, asillustrated, memory device 1070 is connected to both managementcontroller 1010 and wireless management module 1040, but this is notnecessarily so. In particular, memory device 1070 can be connected toonly one of management controller 1010 and wireless management module1040, as needed or desired, and the memory device can be accessed by theunconnected element via the connected element.

In a particular embodiment, wireless transceiver module 1070 is providedwith sufficient power from battery 1080 to operate the wirelesstransceiver module in a listening mode to detect an attempt by mobiledevice 1090 to establish a wireless connection with wireless managementmodule 1040. Here, in response, battery and power manager and timer 1085operates to provide wireless management module 1040 with sufficientpower to authenticate the user of mobile device 1090, and if the user isauthenticated, to place management system 1000 into the wirelesscommunication mode. Here, for example, wireless management module 1040can be configured to hide a SSID, and wireless device 1090 can beconfigured with the SSID and can attempt to establish the wirelessconnection based upon the SSID. Here further, battery and power managerand timer 1085 can be configured to provide wireless transceiver module1070 with power on a periodic basis, in order to conserve power. Forexample, a duty cycle for the listening mode can be determined such thatthe ratio of on-time to off-time provides for sufficient on time topermit reliable detection of an attempt by mobile device 1090 toestablish the wireless connection, while also providing for a minimumpower draw from battery 1080. As such, battery and power manager andtimer 1085 includes timers for providing the duty cycle for listeningmode. In a particular embodiment, the duty cycle timer provides apre-determined duty cycle, or the duty cycle timer provides aconfigurable duty cycle. In another example where battery and powermanager and timer 1085 is configured to provide power on a periodicbasis, the battery and power manager and timer can be configured toprovide power at a predetermined time for a predetermined time interval,such as for five minutes every hour at the bottom of the hour, for onehour every day at 12:00 AM, or at another predetermined time for anotherpredetermined interval, as needed or desired. Here, battery and powermanager and timer 1085 includes a real time clock and one or moreadditional timer, as needed or desired.

In a particular embodiment, the wireless communication mode is enabledto permit the provisioning of management system 1000, the informationhandling system that includes the management system, or both. Here,after mobile device 1090 is wirelessly connected and authenticated towireless management module 1040, the mobile device provides provisioningand configuration information to the wireless management module.Micro-controller 1050 stores the provisioning and configurationinformation 1072 to a memory location in memory device 1070.Provisioning and configuration information 1072 can include informationto configure the operation of management system 1000, such as wirelessaccess information for wireless management module 1040, access andauthentication credentials for access to the management system,management system operating settings for managing the informationhandling system, such as hardware set-points like thermal set-points andcooling fan speed set-points, and other managed configuration settingstypical to the out-of-band management of an information handling systemas are known to the skilled artisan. Provisioning and configurationinformation 1072 can also include information to configure the in-bandoperation of the information handling system, such as a root passwordfor the information handling system, a boot device order, a networksetting, a BIOS setting, or other operational settings for aninformation handling system as are known to the skilled artisan.Further, provisioning and configuration information 1072 can include afirmware image or update for one or more element of management system1000, for one or more element of the information handling system, for aBIOS or UEFI of the information handling system, or for another elementof the information handling system, as needed or desired.

In a particular embodiment, provisioning and configuration information1072 is retained in memory 1070 and is not applied to management system1000 and the information handling system until a later time, such aswhen the information handling system is booted up a next time. Here,when the information handling system is booted up the next time,management controller 1010 retrieves provisioning and configurationinformation 1072 and provides the applicable portions of the informationto management system 1000, to a managed device such as managed device1006, to the in-band environment of the information handling system, oranother element, as needed or desired. In another embodiment,provisioning and configuration information 1072 is applied directly tomanagement system 1000 and the information handling system,substantially when the provisioning and configuration information isreceived from mobile device 1090.

In a particular use case, the provisioning of management system 1000 andthe information handling system permits the in-box provisioning prior toshipment or installation of the information handling system. Forexample, a manufacturer of a server rack can provide the server rackwith certain default configurations in the manufacturing process, andbox-up the server rack. However, prior to shipment, the manufacturer canbecome aware of a critical update related to a particular setting, afirmware version, or the like, or can receive a customer requestedconfiguration for a setting, a firmware version, or the like, and themanufacturer can wirelessly provide the associated provisioning andconfiguration information to the information handling system withouthaving to unbox and power up the server rack. Similarly, the user of theserver rack can wirelessly provide the provisioning and configurationinformation to the information handling system before powering up theserver rack. In this way, the user can provision and configure multipleserver racks in a new data center, or portion thereof, prior to poweringup the server racks. In a particular case, the manufacturer can providea default SSID and default access credentials at the time ofmanufacture, and can provide a user supplied SSID and user providedaccess credentials such that the information handling system cannot betampered with in transit.

In a particular embodiment, battery and power manager and timer 1085configures management system 1000 such that similar provisioning andconfiguration can be performed on an unpowered information handlingsystem as described above, except that, instead of establishing awireless connection to mobile device 1090, the management systemestablishes a USB connection to a USB device connected to USB connector1002. Other than the type of device connected to management system 1000,the use of the USB device provides the same functionality to provisionand configure the management system and the information handling system,as does mobile device 1090. Here, further, where the USB device providesUSB On-The-Go (OTG) functionality, the USB device can also function topower one or more of the elements of management system 1000.

In another embodiment, the wireless communication mode is enabled topermit a user of mobile device 1090 to obtain provisioning andconfiguration information 1072 from memory device 1070, in order toidentify the information handling system that includes management system1000, to identify the current configuration and provisioning version forthe management system or the information handling system, or tootherwise utilize the provisioning and configuration information, asneeded or desired. For example, provisioning and configurationinformation 1072 can be obtained to determine a desired location for theinformation handling system within a datacenter, to determine whether ornot updated provisioning and configuration information is available, orfor other purposes, as needed or desired. Here, provisioning andconfiguration information 1072 can include a MAC address for managementsystem 1000 or for the information handling system, a service tag forthe information handling system, or other information as may be neededor desired to identify the management system or the information handlingsystem. In another example, provisioning and configuration information1072 can include a pointer or path to an OS or disk image repositorythat can be used when the information handling system is first poweredon to provide for the auto-configuration of the information handlingsystem. In yet another example, provisioning and configurationinformation 1072 can be provided to categorize or label the informationhandling system in terms of the service to be provided by theinformation handling system, such as a web server, a database server, anexchange server, a switch/router/bridge, a storage device, or the like.

In another embodiment, the wireless communication mode is enabled afterbattery and power manager and timer 1085 has initiated an inventory modeto provide for the inventorying of the parts and elements of managementsystem 1000, the information handling system that includes themanagement system, or both. Here, battery and power manager and timer1085 operates to provide sufficient power to management controller 1010to monitor and manage the elements of the management system 1000 and ofthe information handling system. As a first matter, the monitoring andmanagement of the elements of management system 1000 and of theinformation handling system includes tracking and maintaining anup-to-date list, or inventory, of the parts that are included on themanagement system and of the information handling system, determining astatus for the parts on the inventory, such as whether or not aparticular part is currently being utilized, and determining whether ornot one or more parts are in need of service or replacement. Managementcontroller 1010 operates to store inventory information 1074 in memorydevice 1070, based upon the inventory, the parts' utilization statuses,and the parts' repair and replacement statuses. Here, after mobiledevice 1090 is wirelessly connected and authenticated to wirelessmanagement module 1040, the mobile device provides inventory information1074 to the mobile device. Battery and power manager and timer 1085 caninitiate the inventory mode on a periodic basis, based upon apredetermined interval, as needed or desired. As such, battery and powermanager and timer 1085 includes one or more timers to determine thepredetermined interval.

Battery 1080 includes a battery power level gauge 1082 that operates todetermine a charge level on the battery. In a particular embodiment,battery and power manager and timer 1085 provides battery power reportfunction in the wireless communication mode, where battery 1080 isconnected to wireless management module 1040, such that the wirelessmanagement module is provided with sufficient power to operate wirelesstransceiver module 1070 to establish and maintain a wireless connectionwith mobile device 1090, and to operate micro-controller 1050 to reportthe battery charge level to mobile device 1090. In a particularembodiment, the battery power report function is provided in response toan attempt by mobile device 1090 to establish and maintain the wirelessconnection with wireless transceiver module 170. In another embodiment,battery and power manager and timer 1085 periodically initiates thebattery power report function. In either embodiment, when theinformation handling system that includes wireless management system1000 is powered off, the battery power level of battery 1080 can bemonitored by a service technician.

Moreover, in a particular embodiment, battery and power manager andtimer 1085 maintains a battery power level threshold, such that, if thebattery power level reported by battery power level gauge 1082 is belowthe battery power level threshold, the battery and power manager andtimer initiates the battery power report function to provide anindication that the battery power level for battery 1080 is low, such astoo low to maintain the data being stored in memory device 1070, or toprovide a back-up data retention mechanism upon power-up of theinformation handling system. In a particular case, battery and powermanager and timer 1085 connects management controller 1010 to battery1080 to provide sufficient power to set an indication in the informationhandling system that the battery power level for battery 1080 is too lowto maintain the data being stored in memory device 1070, so that thepre-boot environment of the information handling system is a aware thatthe data has been lost.

In a particular embodiment, when the pre-boot environment detects theindication that the battery power level for battery 1080 is too low tomaintain the data being stored in memory device 1070, the pre-bootenvironment shuts down the information handling system, or provides aninput option for a service technician to select as to whether to bootthe information handling system using default parameters, or to shutdown the information handling system. In either case, the pre-bootenvironment can provide an error indication that informs the servicetechnician that battery 1080 needs to be charged.

In a first use case, a server that is boxed for shipping can have a lowbattery, and the service technician can provide power to the server forsufficient time to charge the battery prior to first booting up theserver. In another case, the server can be in a storage facility. Inanother embodiment, battery and power manager and timer 1085 includesmultiple battery power level thresholds. A first threshold can indicatea battery power level that is insufficient to maintain the data beingstored in memory device 1070, as described above, and a second thresholdcan indicate a higher battery power level that is associated with awarning indication that the battery power level is getting dangerouslyclose to the first threshold, and that provides the service technicianwith sufficient time to connect power to the server to charge battery1080. In another embodiment, the thresholds are determined based upon acalculation of the amount of battery power level that is needed tomaintain a particular set of configuration information. Thus, for afirst configuration, the battery power level may need to be maintainedat above 25%, while for a second configuration, the battery power levelmay need to be maintained at above 30%.

FIG. 11 illustrates a method for monitoring a battery status in a serverin a data center starting at block 1100. A battery power level isdetected in block 1102. For example, battery power gauge 1085 canprovide an indication as to the power level of battery 1080. A decisionis made as to whether or not the battery power level is below a firstthreshold in decision block 1104. For example, battery and power managerand timer 1085 can include a first threshold level that provides a lowbattery power level warning. If the battery power level is not below thefirst threshold, the “NO” branch of decision block 1104 is taken, and adecision is made as to whether or not a timeout has been met in decisionblock 1106. For example, battery and power manager and timer 1085 caninclude a timer periodically providing an indication as to the powerlevel of battery 1080. If the timeout has not been met, the “NO” branchof decision block 1106 is taken and the method returns to block 1102where the battery power level is detected.

If either the battery power level is below the first threshold and the“YES” branch of decision block 1104 is taken, or the timeout has beenmet and the “YES” branch of decision block 1106, then the methodproceeds to block 1108 where a wireless management system sends abattery power level indication to a wireless device. For example,battery and power manager and timer 1085 can connect battery 1080 towireless management module 1040 to provide sufficient power for thewireless management module to wirelessly connect to mobile device 1090,and the wireless management module can provide an indication of thebattery power level to the mobile device.

A decision is made as to whether or not the battery power level is belowa second threshold in decision block 1110. For example, battery andpower manager and timer 1085 can include a second threshold level thatprovides a battery power level low alert, indicating that the batterypower level of battery 1080 is too low to maintain the data being storedin memory device 1070. If the battery power level is not below thesecond threshold, the “NO” branch of decision block 1110 is taken andthe method returns to block 1102 where the battery power level isdetected. If the battery power level is below the second threshold, the“YES” branch of decision block 1110 is taken, the server is set to a lowbattery power level mode in block 1112, and the method ends in block1114. For example, battery and power manager and timer 1085 can connectbattery 1080 to management controller 1010 to provide sufficient powerfor the management controller to set an indicator in the informationhandling system that the battery power level is low.

FIG. 8 illustrates a generalized embodiment of information handlingsystem 800. For purpose of this disclosure information handling system800 can include any instrumentality or aggregate of instrumentalitiesoperable to compute, classify, process, transmit, receive, retrieve,originate, switch, store, display, manifest, detect, record, reproduce,handle, or utilize any form of information, intelligence, or data forbusiness, scientific, control, entertainment, or other purposes. Forexample, information handling system 800 can be a personal computer, alaptop computer, a smart phone, a tablet device or other consumerelectronic device, a network server, a network storage device, a switchrouter or other network communication device, or any other suitabledevice and may vary in size, shape, performance, functionality, andprice. Further, information handling system 800 can include processingresources for executing machine-executable code, such as a centralprocessing unit (CPU), a programmable logic array (PLA), an embeddeddevice such as a System-on-a-Chip (SoC), or other control logichardware. Information handling system 800 can also include one or morecomputer-readable medium for storing machine-executable code, such assoftware or data. Additional components of information handling system800 can include one or more storage devices that can storemachine-executable code, one or more communications ports forcommunicating with external devices, and various input and output (I/O)devices, such as a keyboard, a mouse, and a video display. Informationhandling system 800 can also include one or more buses operable totransmit information between the various hardware components.

Information handling system 800 can include devices or modules thatembody one or more of the devices or modules described above, andoperates to perform one or more of the methods described above.Information handling system 800 includes a processors 802 and 804, achipset 810, a memory 820, a graphics interface 830, include a basicinput and output system/extensible firmware interface (BIOS/EFI) module840, a disk controller 850, a disk emulator 860, an input/output (I/O)interface 870, a network interface 880, and a management system 890.Processor 802 is connected to chipset 810 via processor interface 806,and processor 804 is connected to the chipset via processor interface808. Memory 820 is connected to chipset 810 via a memory bus 822.Graphics interface 830 is connected to chipset 810 via a graphicsinterface 832, and provides a video display output 836 to a videodisplay 834. In a particular embodiment, information handling system 800includes separate memories that are dedicated to each of processors 802and 804 via separate memory interfaces. An example of memory 820includes random access memory (RAM) such as static RAM (SRAM), dynamicRAM (DRAM), non-volatile RAM (NV-RAM), or the like, read only memory(ROM), another type of memory, or a combination thereof.

BIOS/EFI module 840, disk controller 850, and I/O interface 870 areconnected to chipset 810 via an I/O channel 812. An example of I/Ochannel 812 includes a Peripheral Component Interconnect (PCI)interface, a PCI-Extended (PCI-X) interface, a high speed PCI-Express(PCIe) interface, another industry standard or proprietary communicationinterface, or a combination thereof. Chipset 810 can also include one ormore other I/O interfaces, including an Industry Standard Architecture(ISA) interface, a Small Computer Serial Interface (SCSI) interface, anInter-Integrated Circuit (I²C) interface, a System Packet Interface(SPI), a Universal Serial Bus (USB), another interface, or a combinationthereof. BIOS/EFI module 840 includes BIOS/EFI code operable to detectresources within information handling system 800, to provide drivers forthe resources, initialize the resources, and access the resources.BIOS/EFI module 840 includes code that operates to detect resourceswithin information handling system 800, to provide drivers for theresources, to initialize the resources, and to access the resources.

Disk controller 850 includes a disk interface 852 that connects the disccontroller to a hard disk drive (HDD) 854, to an optical disk drive(ODD) 856, and to disk emulator 860. An example of disk interface 852includes an Integrated Drive Electronics (IDE) interface, an AdvancedTechnology Attachment (ATA) such as a parallel ATA (PATA) interface or aserial ATA (SATA) interface, a SCSI interface, a USB interface, aproprietary interface, or a combination thereof. Disk emulator 860permits a solid-state drive 864 to be connected to information handlingsystem 800 via an external interface 862. An example of externalinterface 862 includes a USB interface, an IEEE 1394 (Firewire)interface, a proprietary interface, or a combination thereof.Alternatively, solid-state drive 864 can be disposed within informationhandling system 800.

I/O interface 870 includes a peripheral interface 872 that connects theI/O interface to an add-on resource 874, to a TPM 876, and to networkinterface 880. Peripheral interface 872 can be the same type ofinterface as I/O channel 812, or can be a different type of interface.As such, I/O interface 870 extends the capacity of I/O channel 812 whenperipheral interface 872 and the I/O channel are of the same type, andthe I/O interface translates information from a format suitable to theI/O channel to a format suitable to the peripheral channel 872 when theyare of a different type. Add-on resource 874 can include a data storagesystem, an additional graphics interface, a network interface card(NIC), a sound/video processing card, another add-on resource, or acombination thereof. Add-on resource 874 can be on a main circuit board,on separate circuit board or add-in card disposed within informationhandling system 800, a device that is external to the informationhandling system, or a combination thereof.

Network interface 880 represents a NIC disposed within informationhandling system 800, on a main circuit board of the information handlingsystem, integrated onto another component such as chipset 810, inanother suitable location, or a combination thereof. Network interfacedevice 880 includes network channels 882 and 884 that provide interfacesto devices that are external to information handling system 800. In aparticular embodiment, network channels 882 and 884 are of a differenttype than peripheral channel 872 and network interface 880 translatesinformation from a format suitable to the peripheral channel to a formatsuitable to external devices. An example of network channels 882 and 884includes InfiniBand channels, Fibre Channel channels, Gigabit Ethernetchannels, proprietary channel architectures, or a combination thereof.Network channels 882 and 884 can be connected to external networkresources (not illustrated). The network resource can include anotherinformation handling system, a data storage system, another network, agrid management system, another suitable resource, or a combinationthereof.

Management controller 890 provides for out-of-band monitoring,management, and control of the respective elements of informationhandling system 800, such as cooling fan speed control, power supplymanagement, hot-swap and hot-plug management, firmware management andupdate management for system BIOS or UEFI, Option ROM, device firmware,and the like, or other system management and control functions as neededor desired. As such, management system 890 provides some or all of thefunctions and features of the management systems described herein.

The preceding description in combination with the Figures is provided toassist in understanding the teachings disclosed herein. The precedingdiscussion focused on specific implementations and embodiments of theteachings. This focus has been provided to assist in describing theteachings, and should not be interpreted as a limitation on the scope orapplicability of the teachings. However, other teachings can certainlybe used in this application. The teachings can also be used in otherapplications, and with several different types of architectures, such asdistributed computing architectures, client/server architectures, ormiddleware server architectures and associated resources.

Although only a few exemplary embodiments have been described in detailherein, those skilled in the art will readily appreciate that manymodifications are possible in the exemplary embodiments withoutmaterially departing from the novel teachings and advantages of theembodiments of the present disclosure. Accordingly, all suchmodifications are intended to be included within the scope of theembodiments of the present disclosure as defined in the followingclaims. In the claims, means-plus-function clauses are intended to coverthe structures described herein as performing the recited function andnot only structural equivalents, but also equivalent structures.

When referred to as a “device,” a “module,” or the like, the embodimentsdescribed herein can be configured as hardware. For example, a portionof an information handling system device may be hardware such as, forexample, an integrated circuit (such as an Application SpecificIntegrated Circuit (ASIC), a Field Programmable Gate Array (FPGA), astructured ASIC, or a device embedded on a larger chip), a card (such asa Peripheral Component Interface (PCI) card, a PCI-express card, aPersonal Computer Memory Card International Association (PCMCIA) card,or other such expansion card), or a system (such as a motherboard, asystem-on-a-chip (SoC), or a stand-alone device).

The device or module can include software, including firmware embeddedat a device, such as a Pentium class or PowerPC™ brand processor, orother such device, or software capable of operating a relevantenvironment of the information handling system. The device or module canalso include a combination of the foregoing examples of hardware orsoftware. Note that an information handling system can include anintegrated circuit or a board-level product having portions thereof thatcan also be any combination of hardware and software.

Devices, modules, resources, or programs that are in communication withone another need not be in continuous communication with each other,unless expressly specified otherwise. In addition, devices, modules,resources, or programs that are in communication with one another cancommunicate directly or indirectly through one or more intermediaries.

The above-disclosed subject matter is to be considered illustrative, andnot restrictive, and the appended claims are intended to cover any andall such modifications, enhancements, and other embodiments that fallwithin the scope of the present invention. Thus, to the maximum extentallowed by law, the scope of the present invention is to be determinedby the broadest permissible interpretation of the following claims andtheir equivalents, and shall not be restricted or limited by theforegoing detailed description.

What is claimed is:
 1. An information handling system, comprising: abattery including a battery power level gauge that determines a powerlevel of the battery; a processor; and a management system including abaseboard management controller (BMC) and a wireless transceiver,wherein when the processor is unpowered, the BMC is coupled to receivepower from the battery, the BMC provides a first indication of the powerlevel of the battery via the wireless transceiver to a mobile device,and sets a second indication for use by the processor during a pre-bootoperation when the processor is subsequently powered on, wherein the BMCprovides the first indication when the power level of the battery isbelow a first threshold; wherein the information handling system detectsthe second indication during the pre-boot operation, and shuts down thepre-boot operation and provides an error indication in response todetecting the second indication.
 2. The information handling system ofclaim 1, wherein the BMC periodically provides the first indication. 3.The information handling system of claim 1, further comprising: a memorydevice coupled to receive power from the battery to maintain data storedin the memory device when the processor is unpowered.
 4. The informationhandling system of claim 3, wherein the first threshold indicates afirst power level of the battery, below which the memory device isunable to maintain the data stored therein.
 5. The information handlingsystem of claim 4, wherein the BMC provides a third indication of thepower level of the battery via the wireless transceiver when the powerlevel of the battery is above the first threshold but is below a secondthreshold, the third indication providing a warning that the power levelof the battery is approaching the first threshold.
 6. The informationhandling system of claim 1, further comprising: a low batteryindication, wherein the BMC sets the low battery indication in responseto providing the first indication.
 7. The information handling system ofclaim 6, wherein, when the low battery indication is set, theinformation handling system will not boot.
 8. The information handlingsystem of claim 7, wherein further, when the low battery indication isset, the information handling system provides an option to boot with adefault setting.
 9. The information handling system of claim 7, wherein,when the battery is charged to a high power level, the low batteryindication is reset, the high power level being higher than the firstthreshold.
 10. A method, comprising: determining a power level of abattery of an information handling system; coupling a baseboardmanagement controller (BMC) to receive power from the battery when aprocessor of the information handling system is unpowered; providing, bya wireless transceiver coupled to the BMC, a first indication of thepower level of the battery to a mobile device, wherein the BMC providesthe first indication when the power level of the battery is below afirst threshold; setting, by the BMC, a second indication for use by theprocessor during a pre-boot operation when the processor is subsequentlypowered on; detecting, by the information handling system, the secondindication during the pre-boot operation; shutting down, by theinformation handling system, the pre-boot operation in response todetecting the second indication; and providing, by the informationhandling system, an error indication in further response to detectingthe second indication.
 11. The method of claim 10, wherein the firstindication is provided periodically.
 12. The method of claim 10, furthercomprising: coupling a memory device of the information handling systemto receive power from the battery to maintain data stored in the memorydevice when the processor is unpowered.
 13. The method of claim 12,wherein the first threshold indicates a first power level of thebattery, below which the memory device is unable to maintain the datastored therein.
 14. The method of claim 13, further comprising:providing, by the wireless transceiver, a third indication of the powerlevel of the battery when the power level of the battery is above thefirst threshold but is below a second threshold, the third indicationproviding a warning that the power level of the battery is approachingthe first threshold.
 15. The method of claim 10, further comprising:setting a low battery indication of the information handling system inresponse to providing the first indication.
 16. The method of claim 15,further comprising: preventing the information handling system frombooting when the low battery indication is set.
 17. A non-transitorycomputer-readable medium including code for performing a method, themethod comprising: determining a power level of a battery of aninformation handling system; coupling a BMC to receive power from thebattery when a processor of the information handling system isunpowered; providing, by a wireless transceiver coupled to the BMC, afirst indication of the power level of the battery to a mobile device,wherein the BMC provides the first indication when the power level ofthe battery is below a first threshold; setting, by the BMC, a secondindication for use by the processor during a pre-boot operation when theprocessor is subsequently powered on; detecting, by the informationhandling system, the second indication during the pre-boot operation;shutting down the pre-boot operation in response to detecting the secondindication; and providing an error indication in further response todetecting the second indication.
 18. The computer-readable medium ofclaim 17, wherein the indication is provided periodically.